-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation of rlp::decode() #405
Conversation
I clearly misunderstood the assignment that I have been given. I indeed thought that I was asked to implement the whole I am terribly sorry if whatever I have done here is completly out of scope! I'm well aware some code will need to be removed but pushing now allow me to clarify this confusion with you guys so I can finish what I have been asked! |
The scope of this PR is too large. Could you break it down into two PRs, one for the RLP trait & RLP decode |
003d4c2
to
7c69d8c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
almos lgtm now wdyt @Eikix
agreed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, proposed variable name changes to make it easier to understand on first read.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation of rlp::decode() as it was benchmarked and tested here (https://github.com/danilowhk/cairo-lib/blob/main/src/encoding/rlp.cairo).
Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
Resolves: #
What is the new behavior?
Does this introduce a breaking change?